Barcode Pattern Extended

Reference: PBI 303248
Compliance Impacts: This defect is not a compliance or regulatory issue.
Documentation: Document Generation Services API Reference Guide

Summary

Previously, if a customer defined a barcode pattern in the AncillaryOutputOptions, the BRCD value would automatically print in the first position of the barcode if it were defined in the requirements document even though the value was not passed as part of the pattern.

Technical Notes

Now, when a customer makes a request to the Expere Engine and implements the AncillaryOutputOptions for a barcode, the placement value for the BRCD will be honored correctly. Multiple BRCD values can be placed in the requirements document and included into the pattern. Any value not specified in the pattern is ignored and does not appear in the generated barcode.

Example: Following is an example of an AncillaryOutputOptions submitted on a request that will generate a barcode without the BRCD.

<exp:Barcode>
 <exp:Pattern>Page_%page%_of_%totalpages%_%date%_Doc_%docsequence%_of_%docsequencetotal%</exp:Pattern>
</exp:Barcode>

Following is an example of an AncillaryOutputOptions submitted on a request that will generate a barcode with the BRCD value when defined in the requirements document.

<exp:Barcode>
 <exp:Pattern>Page_%page%_of_%totalpages%_%date%_%BRCD%_Doc_%docsequence%_of_%docsequencetotal%</exp:Pattern>
</exp:Barcode>

Note: For details on how to implement and author the custom BRCD values, refer to the Document Generation Services API Reference Guide